ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2024-12-29 17:28:53 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
12,683 Commits 185 Branches 90 Tags 89 MiB
2e54382611
Commit Graph

102 Commits

Author SHA1 Message Date
Sajith Sasidharan
573ab8768b Re-title "use pip cache" step in GitHub Actions 2021-01-18 11:08:56 -05:00
Sajith Sasidharan
27a122088c Use pip cache on GitHub Actions 
Using the method outlined in https://github.com/actions/cache/blob/main/examples.md#using-pip-to-get-cache-location
 2021-01-18 11:02:55 -05:00
Sajith Sasidharan
fa1a8e8371 Upgrade pip used in GitHub Actions 
From pip 20.1+ onward, "pip cache dir" can be used to find location of
pip cache, and this is useful across all three major OSes supported by
GitHub Actions.
 2021-01-18 10:58:12 -05:00
Jean-Paul Calderone
e72c93a982 explain why we're not using the github action here 2021-01-08 08:52:38 -05:00
Jean-Paul Calderone
5614c4c3f4 improve this comment marginally 
just looking for an excuse to trigger another build and see if inviting
"coveralls" to be a collaborator on LeastAuthority/tahoe-lafs fixes the status
reporting issue.
 2021-01-08 08:27:00 -05:00
Jean-Paul Calderone
709823e562 most of those words proved irrelevant 2021-01-07 18:24:57 -05:00
Jean-Paul Calderone
3b8df95e3e Try constructing build_num differently for push 2021-01-06 21:09:33 -05:00
Jean-Paul Calderone
e382ef8a89 Clean up the explanation, link to some more/better stuff 2021-01-06 20:27:41 -05:00
Jean-Paul Calderone
f5ba293f79 Ideally this is no longer necessary 2021-01-06 20:27:17 -05:00
Jean-Paul Calderone
e3a6f43dc9 less shell wankery 2021-01-06 16:43:11 -05:00
Jean-Paul Calderone
59e385c00f apparently it doesn't have remotes in there 2021-01-06 16:24:53 -05:00
Jean-Paul Calderone
d515887ba1 This is probably faster and may actually work 
`git fetch --prune --unshallow` doesn't seem to get
refs/remotes/pull/<PR>/merge but that's okay because HEAD is already set to that
 2021-01-06 16:16:36 -05:00
Jean-Paul Calderone
89c54af01d Guess we need the rest of the repo too, surprise. 2021-01-06 16:05:35 -05:00
Jean-Paul Calderone
fac12210cb Can't do that Git stuff without a checkout 
Maybe *that* is why `coveralls --finish` fails?
 2021-01-06 15:58:48 -05:00
Jean-Paul Calderone
52c42b5118 dump this info, who knows how many more rounds this will take 2021-01-06 15:48:20 -05:00
Jean-Paul Calderone
24a531474d So much for my ability to read and understand a Python program 
coveralls complained:

{"error":"No build matching CI build number 467026020 found"}

So try constructing a build_num that looks like the value we observed from
`coveralls` output when it was submitting coverage data.
 2021-01-06 15:38:12 -05:00
Jean-Paul Calderone
4d2782c178 Hahaha. Resolve the variable, don't just include its name. 2021-01-06 14:57:31 -05:00
Jean-Paul Calderone
8e8a7d82c6 it was one or the other. turns out it was the other. 2021-01-06 14:33:31 -05:00
Jean-Paul Calderone
f24cc5da0c The angrier I am the more words I write 2021-01-06 14:33:00 -05:00
Jean-Paul Calderone
adf3518fc1 Okay I guess that served its purpose 2021-01-06 14:32:48 -05:00
Jean-Paul Calderone
4b65751f51 Debug the earlier submissions to see what build_num they're providing 2021-01-06 09:01:08 -05:00
Jean-Paul Calderone
f3aca51e35 run in debug mode to collect info for bug report 2021-01-05 20:52:02 -05:00
Jean-Paul Calderone
9a8a61b740 Further tweaks to help the last step 2021-01-05 20:31:32 -05:00
Jean-Paul Calderone
bebcca39f6 Switch to coveralls-python, maybe it works better 2021-01-05 20:09:46 -05:00
Jean-Paul Calderone
3fb412eda1 Perhaps this is the correct github-token to use. 
The coveralls docs might be wrong.
 2021-01-05 16:20:41 -05:00
Jean-Paul Calderone
13bcd8170b Turn on Coveralls on GitHub actions 2021-01-05 15:57:10 -05:00
Viktoriia
3a0b72f34c
Update CONTRIBUTING.rst 
Changed 'Coding Standard' to 'Coding Standards'
 2020-12-15 14:11:26 +02:00
viktoriiasavchuk
8d439fd58d
Update CONTRIBUTING.rst 
Added link to the Contributor Code of Conduct, https://github.com/tahoe-lafs/tahoe-lafs/blob/master/docs/CODE_OF_CONDUCT.md
 2020-12-13 20:59:58 +02:00
Sajith Sasidharan
c8aab085d7 Re-introduce vcpython27 in GitHub Actions 
Turns out that netifaces has not published a .whl package for Python
2.7 and 64-bit Windows.
 2020-11-25 08:17:40 -05:00
Sajith Sasidharan
525f2201c6 Do not install vcpython27 during Windows CI steps 
With zfec 1.5.4, wheel packages for Windows is available now.
Installing a compiler is no longer necessary.
 2020-10-15 14:17:53 -04:00
Jean-Paul Calderone
e107e11079 Remove references to the bare "coverage" tox environment 
* We stopped using Appveyor a while ago so entirely remove its configuration.
* There's no release step where coverage information is *examined* so why
  collect it?
* Switch GitHub Actions config to py27-coverage tox environment
 2020-08-27 10:37:50 -04:00
Sajith Sasidharan
9b68b484bd Run integration tests on Windows on GitHub Actions 
Integration tests are currently not run on Windows, because they
turned out to be a little unreliable: sometimes they fail, and when
that happens restarting the test would make things pass.

We will re-enable them and see what happens.
 2020-06-22 16:32:26 -04:00
Sajith Sasidharan
4b1ff9546c Do not install setuptools in pyinstaller step 
This is unnecessary, and likely was the result of copy-pasting.
 2020-05-13 12:06:11 -04:00
Sajith Sasidharan
f3d37e52db Upload PyInstaller package as a GitHub Actions artifact 2020-05-12 18:37:50 -04:00
Sajith Sasidharan
86184e9aa9 Do not install codecov in GitHub Actions packaging tests 2020-05-12 18:28:42 -04:00
Sajith Sasidharan
b1d7e99671 Try running PyInstaller-generated binary in GitHub Actions 2020-05-12 18:15:17 -04:00
Jean-Paul Calderone
e336d977dd
Filter push trigger down to master branch 2020-04-13 12:19:41 -04:00
Sajith Sasidharan
a38029f9db Remove on.release from workflow triggers 
Per GitHub's documentation for on.release events, `on.release` event
will run our workflow any time the `release` event occurs, but it is
unclear if Tahoe will need this yet.  Removing for now.
 2020-03-06 14:13:05 -05:00
Sajith Sasidharan
c4061fffa0 Fearlessly use codecov.io token 2020-02-27 23:15:51 -05:00
Sajith Sasidharan
29947aad86 Don't run coverage tests on Ubuntu 2020-02-26 09:19:37 -05:00
Sajith Sasidharan
9752d6a2ff Don't run tests periodically 
While working on the PR, I never saw this actually working.
 2020-02-26 09:15:02 -05:00
Sajith Sasidharan
2d0cf3d3c3 Upload integration.eliot.json if integration tests fail 2020-02-26 09:11:23 -05:00
Sajith Sasidharan
5ba0ba787f Omit codechecks 2020-02-26 09:09:54 -05:00
Sajith Sasidharan
d996cc8d11 Fix a syntax error 
Per GitHub, this is not fine:

    - name: [Windows] Do stuff
      run: ...

This is fine:

    - name: Do stuff [Windows]
      run: ...
 2020-02-25 23:17:45 -05:00
Sajith Sasidharan
4924cd9c04 Run "tox -e pyinstaller" in a separate step 2020-02-25 23:10:26 -05:00
Sajith Sasidharan
383b102b78 Run integration tests 
Run integration tests only on macOS for now, because on Windows and
Ubuntu integration tests get stuck and time out after six hours.
 2020-02-25 23:05:03 -05:00
Sajith Sasidharan
1a4ae0fc81 Remove "tox -e py27" 
Running "tox -e coverage" is sufficient.
 2020-02-25 23:02:35 -05:00
Sajith Sasidharan
c535b83f06 Rename "test" to "coverage" 2020-02-25 23:02:02 -05:00
Sajith Sasidharan
77c6b39a70 Update a name 2020-02-25 23:01:29 -05:00
Sajith Sasidharan
afdfb48ee1 Run codechecks, but continue on error. 2020-02-25 22:59:04 -05:00
Sajith Sasidharan
5862e1bea3 Use GitHub Actions for CI. 
Fixes: ticket:3277
 2020-02-20 22:19:21 -05:00
Jean-Paul Calderone
99318ab363 Skeleton that mostly links to existing documentation 2019-03-15 13:11:21 -04:00