Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jul 03 18:07
    pwhack commented #1551
  • Jul 03 14:08
    SchoolGuy closed #3088
  • Jul 03 14:08
    SchoolGuy commented #3088
  • Jul 03 14:07
    SchoolGuy unassigned #2209
  • Jul 03 13:55
    SchoolGuy labeled #2665
  • Jul 03 13:54
    SchoolGuy commented #2665
  • Jul 03 13:50
    codecov[bot] commented #2897
  • Jul 03 13:49
    codecov[bot] commented #3145
  • Jul 03 13:49
    codecov[bot] commented #2884
  • Jul 03 13:45
    SchoolGuy synchronize #3167
  • Jul 03 13:45

    SchoolGuy on reposync-overhaul

    Tests: Add for Cobbler report a… Tests: Refactor for reposync ac… Actions: Reposync - Cleanup wit… and 1 more (compare)

  • Jul 03 13:39
    SchoolGuy milestoned #1551
  • Jul 03 13:39
    SchoolGuy demilestoned #1551
  • Jul 03 13:39
    SchoolGuy assigned #1551
  • Jul 03 13:38
    SchoolGuy closed #1551
  • Jul 03 13:38
    SchoolGuy commented #1551
  • Jul 03 12:33
    SchoolGuy assigned #3033
  • Jul 03 12:29
    github-actions[bot] labeled #3167
  • Jul 03 12:29
    SchoolGuy opened #3167
  • Jul 03 12:29
    SchoolGuy milestoned #3167
consus
@consus:matrix.org
[m]
I was expecting a failure
egotthold
@egotthold:matrix.org
[m]
Should we merge and then check if it is working?
consus
@consus:matrix.org
[m]
But it's just silently ignored
If that's okay with you
egotthold
@egotthold:matrix.org
[m]
Is there a reason why we can't put this into a single workflow?
Nvm saw the example from the Action.
So yeah. Cleanup what you want and then I'll merge. If it fails we fix it with a followup PR. Not nice but we have no other choice afaik.
consus
@consus:matrix.org
[m]
I expect this to work on master
So we can do this right ahead
egotthold
@egotthold:matrix.org
[m]
Okay. Git is clean in your eyes? consus
consus
@consus:matrix.org
[m]
Yeah
egotthold
@egotthold:matrix.org
[m]
consus still not triggered
it kinda is
but failed
egotthold
@egotthold:matrix.org
[m]
What
Ah okay
Yeah but that is a problem with XML?
consus
@consus:matrix.org
[m]
I think so
Found it: The outer<testsuites> is not expected and causes issues. trimming those and it works.
Hmm
I guess that's the problem
Someone being naughty and not follows the spec
I'm not sure who though xD
k, should be fine now
consus
@consus:matrix.org
[m]
Nah, it requires some attributes that should be optional
Goddamit
egotthold
@egotthold:matrix.org
[m]
Okay. Just ping me once it is ready.
consus
@consus:matrix.org
[m]
Screw that
It seems that Github Actions sucks dick
The test report cannot be bigger than 65k bytes and no screenshots, no links, nothing
As a bonus Check Jobs cannot be properly positioned in multi-workflow build
So the result will pop under random workflows
I suggest Allure and GitHub pages
We can paste the unit test results there too
egotthold
@egotthold:matrix.org
[m]
consus How did you come to that conclusion with 65kb? It seems rather small.
consus
@consus:matrix.org
[m]
I've read the full documentation to test-reporter :/
Maximum report size is 65535 bytes. Input parameters list-suites and list-tests will be automatically adjusted if max size is exceeded.
Check Runs are created for specific commit SHA. It's not possible to specify under which workflow test report should belong if more workflows are running for the same SHA. Thanks to this GitHub "feature" it's possible your test report will appear in an unexpected place in GitHub UI. For more information, see #67.
That's why we haven't seen the report: it was hidden under the different workflow tab
egotthold
@egotthold:matrix.org
[m]
Okay well the 65kb is a blocker. The other thing is just inconvenient. Can we maybe upload the test results to codacy?
Afaik they support test results
Check this out
This plugin allow pasting to GH pages with reference links left in the Checks section
egotthold
@egotthold:matrix.org
[m]
Okay let's do it! It looks nice, use friendly and we don't introduce a new provide like Gitlab, Bitbucket, CircleCI or however they are called.
I've updated the guide