You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The build agent seems to include the commit message somewhere (or it may just look into it for instructions like skip_ci).
If I remember correctly this does not happen when triggering the "rebuild incomplete", which would then make the "internal inspection" more likely.
During this some escaping is missing, which leads - from time to time - to a broken build.
Example commit message (svn) leading to this issue:
adjustments for VALUE handling, restoring the pre 3.2-handling of using "VALUES" for an elementary item
cobc:
* parser.y (value_clause): handle simple VALUES without any optional phrases and with only a single value explicit not as table-format but as if VALUE was specified (raising a warning/error depending on relax-syntax-checks), as at least XicroLocus has this non-standard (and undocumented) extension
* field.c (validate_elem_value): explicit check that non-occurs item has only a single value
* parser.y (value_clause): improved parsing for table-format
tests/testsuite.src:
* syn_misc.at, syn_value.at: moved OCCURS too many VALUES to syn_value.at
The text was updated successfully, but these errors were encountered:
The build agent seems to include the commit message somewhere (or it may just look into it for instructions like skip_ci).
If I remember correctly this does not happen when triggering the "rebuild incomplete", which would then make the "internal inspection" more likely.
During this some escaping is missing, which leads - from time to time - to a broken build.
Example commit message (svn) leading to this issue:
The text was updated successfully, but these errors were encountered: