Here is a failed Jenkins log:
https://ci.int.devshift.net/blue/organizations/jenkins/service-uhc-portal-pr-check/detail/service-uhc-portal-pr-check/4530/pipeline

• it is hard to tell if linting/prettier or unit tests failed

  [eliran] shouldn't be that hard - you can search for exited with code - there's one per task. are we interested in making this more visible? we could possibly tinker with concurrently and achieve that.

   [davet] yes, more visible like GitLab pipelines were.  BTW emalka@redhat.com, do we need a card to move Cypress to Jenkins?

• can we change the ascii and/or jenkins viewer to show the graphics rather than "���"

  [eliran] symbols are system dependent (or browser, but that's the same cuz it's derivable), so this might be out of our reach. if these messages are from within uhc-portal, we could update them to remove symbols, but I doubt we'd have any control of their rendering.

  [davet] in ocp land we were able to ask for a particular ascii set/ut-8 or something which resolved the rendering, not sure if it is the same in OCM land.

• can we make the log output less verbose, perhaps only outputting errors/failures, else "Success" ?

  [eliran] we shouldn't - how would you investigate errors, in case they appear? we can't know that in advance, so shouldn't tune our logs to remove data useful for investigation.

• can we output at least section dividers in the log?  Ex "*************** Unit Tests *****************", maybe multi-lined for more emphasis

  [eliran] possibly - see first answer