donkirkby/live-py-plugin

Test Emacs version on GitHub Actions

Open

#309 opened on Jul 2, 2021

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Python (63 forks)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (302 stars)
PR merge metrics
 (PR metrics pending)

Description

What I did

Added the Emacs ERT tests to the GitHub Actions workflow, after TravisCI stopped working.

What happened

It complained with this error:

emacs: standard input is not a tty

What I wanted to happen

Run the way it used to on Travis.

Analysis

I found a bunch of actions to help:

  • setup emacs
  • emacs lisp check I haven't tried it yet, but it looks like it can run ERT.
  • cask I used it on Travis, but I think it's not needed with setup emacs.
  • There's some discussion on actions/runner#241. That's where I learned about script and scriptreplay.

Contributor guide

Research direction
Examine the GitHub Actions workflow file and the Emacs test setup. Investigate how TravisCI ran the tests and compare with the current GitHub Actions configuration. Look into the `script` command or the `setup emacs` action to resolve the 'standard input is not a tty' error.
Tech stack
github actionsshell
Domain
ci cdtesting
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75